Process Control Communication Architecture

ABSTRACT

A platform-to-platform communication architecture for a process control messaging service in a process control system or other industrial setting allows stationary and portable industrial computing units to communicate with each other, in one-to-one and one-to-many communications, and across networks, including isolated networks inside the process control system or industrial setting and external networks. A requesting industrial computing device platform generates a message for a destination, or responding, industrial computing device in the communication protocol of the destination platform, and wraps the message in a communication protocol of the process control messaging service. The communication architecture decodes the wrapped message into the communication protocol of the destination industrial computing device and forwards the decoded wrapped message to the destination. The communication architecture allows for a variety of communication services, including, but not limited to, instant/real-time peer-to-peer messaging, time synchronization, automatic data transfer with an asset management system, communication with field devices via an asset management system and large data transfers.

TECHNICAL FIELD

The present disclosure relates generally to process control systems, and, more particularly, to a process control communication architecture for communication among industrial computing devices in a process control system.

BACKGROUND

Distributed process control systems, like those used in chemical, petroleum or other processes, typically include one or more process controllers and input/output (I/O) devices communicatively coupled to at least one host or operator workstation and to one or more field devices via analog, digital or combined analog/digital buses, or via a wireless communication link or network.

A process controller (sometimes referred to as a “controller”), which is typically located within the plant or other industrial environment, receives signals (sometimes referred to as “control inputs”) indicative of process measurements and uses the information carried by these signals to implement control routines that cause the controller to generate control signals (sometimes referred to as “control outputs”) based on the control inputs and the internal logic of the control routines. The controllers send the generated control signals over buses or other communication links to control operation of field devices. In some instances, the controllers may coordinate with control routines implemented by smart field devices, such as Highway Addressable Remote Transmitter (HART®), WirelessHART®, and FOUNDATION® Fieldbus (sometimes just called “Fieldbus”) field devices. Moreover, in many cases, there may be plant or other industrial equipment that operates in the plant or other industrial setting to perform some function that is not under direct control of the process controller, such as vibration detection equipment, rotating equipment, electrical power generating equipment, etc.

The field devices that are typically associated with controller, which may be, for example, valves, valve positioners, switches, and transmitters (e.g., temperature, pressure, level and flow rate sensors), are located within the process environment and generally perform physical or process control functions. For example, a valve may open or close in response to a control output received from a controller, or may transmit to a controller a measurement of a process parameter so that the controller can utilize the measurement as a control input. Smart field devices, such as field devices conforming to the well-known Fieldbus protocol may also perform control calculations, alarming functions, and other control functions commonly implemented within a controller. Field devices may be configured to communicate with controllers and/or other field devices according to various communication protocols. For example, a plant may include traditional analog 4-20 mA field devices, HART® field devices, Fieldbus field devices, and/or other types of field devices.

The process controllers receive signals indicative of process measurements made by sensors or field devices and/or other information pertaining to the field devices and execute a controller application that runs, for example, different control modules that make process control decisions, generate control signals based on the received information, and coordinate with the control modules or blocks being performed in the field devices. The control modules in the controller send the control signals over the communication lines or links to the field devices to thereby control the operation of at least a portion of the process plant or system.

Information from the field devices and the controller is usually made available over a data highway to one or more other hardware devices, such as operator workstations, personal computers, or computing devices, data historians, report generators, centralized databases, or other centralized administrative computing devices that are typically, but not always, placed in control rooms or other locations away from the harsher plant environment. Each of these hardware devices typically, though not always, is centralized across the process plant or across a portion of the process plant. These hardware devices run applications that may, for example, enable an operator to perform functions with respect to controlling a process and/or operating the process plant, such as changing settings of the process control routine, modifying the operation of the control modules within the controllers or the field devices, viewing the current state of the process, viewing alarms generated by field devices and controllers, simulating the operation of the process for the purpose of training personnel or testing the process control software, keeping and updating a configuration database, etc. The data highway utilized by the hardware devices, controllers, and field devices may include a wired communication path, a wireless communication path, or a combination of wired and wireless communication paths.

As an example, the DeltaV™ control system, sold by Emerson Process Management, includes multiple applications stored within and executed by different devices located at diverse places within a process plant. A configuration application, which resides in one or more operator workstations or computing devices, enables users to create or change process control modules and download these process control modules via a data highway to dedicated distributed controllers. Typically, these control modules are made up of communicatively interconnected function blocks, which perform functions within the control scheme based on inputs thereto and which provide outputs to other function blocks within the control scheme. The configuration application may also allow a configuration designer to create or change operator interfaces which are used by a viewing application to display data to an operator and to enable the operator to change settings, such as set points, within the process control routines. Each dedicated controller and, in some cases, one or more field devices, stores and executes a respective controller application that runs the control modules assigned and downloaded thereto to implement actual process control functionality. The viewing applications, which may be executed on one or more operator workstations (or on one or more remote computing devices in communicative connection with the operator workstations and the data highway), receive data from the controller application via the data highway and display this data to process control system designers, operators, or users using the operator interfaces, and may provide any of a number of different views, such as an operator's view, an engineer's view, a technician's view, etc. A data historian application is typically stored in and executed by a data historian device that collects and stores some or all of the data provided across the data highway while a configuration database application may run in a still further computer attached to the data highway to store the current process control routine configuration and data associated therewith. Alternatively, the configuration database may be located in the same workstation as the configuration application.

As noted above, operator display applications are typically implemented on a system wide basis in one or more of the workstations and provide displays to the operator or maintenance persons regarding the operating state of the control system or the devices within the plant. Typically, these displays take the form of alarming displays that receive alarms generated by controllers or devices within the process plant, control displays indicating the operating state of the controllers and other devices within the process plant, maintenance displays indicating the operating state of the devices within the process plant, etc. These displays are generally configured to display, in known manners, information or data received from the process control modules or the devices within the process plant. In some known systems, displays have a graphic associated with a physical or logical element that is communicatively tied to the physical or logical element to receive data about the physical or logical element. The graphic may be changed on the display screen based on the received data to illustrate, for example, that a tank is half full, to illustrate the flow measured by a flow sensor, etc.

Traditional analog 4-20 mA field devices communicate with a controller via a two-wire communication link (sometimes called a “loop” or “current loop”) configured to carry a 4-20 mA DC signal indicative of a measurement or control command. For example, a level transmitter may sense a tank level and transmit via the loop a current signal corresponding to that measurement (e.g., a 4 mA signal for 0% full, a 12 mA signal for 50% full, and a 20 mA signal for 100% full). The controller receives the current signal, determines the tank level measurement based on the current signal, and takes some action based on the tank level measurement (e.g., opening or closing an inlet valve). Analog 4-20 mA field devices typically come in two varieties including four-wire field devices and two-wire field devices. A four-wire field device typically relies on a first set of wires (i.e., the loop) for communication, and a second set of wires for power. A two-wire field device relies on the loop for both communication and power. These two-wire field devices may be called “loop powered” field devices.

Process plants often implement traditional 4-20 mA systems due to the simplicity and effectiveness of the design. Unfortunately, traditional 4-20 mA current loops only transmit one process signal at a time. Thus, a set-up including a control valve and a flow transmitter on a pipe carrying material may require three separate current loops: one for carrying a 4-20 mA signal indicative of a control command for the valve (e.g., to move the valve to 60% open); a second for carrying a 4-20 mA signal indicative of the valve's actual position (e.g., so that the controller knows the degree to which the valve has responded to control commands); and a third for carrying a 4-20 mA signal indicative of a measured flow. As a result, a traditional 4-20 mA set-up in a plant having a large number of field devices may require extensive wiring, which can be costly and can lead to complexity when setting up and maintaining the communication system.

More recently, the process control industry has moved to implement digital communications within the process control environment. For example, the HART® protocol uses the loop DC magnitude to send and receive analog signals, but also superimposes an AC digital carrier signal on the DC signal to enable two-way field communications with smart field instruments. As another example, the Fieldbus protocol provides all-digital communications on a two-wire bus (sometimes called a “segment” or “Fieldbus segment”). This two-wire Fieldbus segment can be coupled to multiple field devices to provide power to the multiple field devices (via a DC voltage available on the segment) and to enable communication by the field devices (via an AC digital communication signal superimposed on the DC power supply voltage). Generally speaking, because the connected field devices use the same segment for communication and are connected in parallel, only one field device can transmit a message at any given time over the segment. Accordingly, communication on a segment is coordinated by a device designated as a link active scheduler (LAS). The LAS is responsible for passing a token between field devices connected to the segment. Only the device with the token may communicate over the segment at a particular time.

These digital communication protocols generally enable more field devices to be connected to a particular communication link, support more and faster communications between the field devices and the controller, and/or allow field devices to send more and different types of information (such as information pertaining to the status and configuration of the field device itself) to the process controller and other devices in or connected to the control network. Furthermore, these standard digital protocols enable field devices made by different manufacturers to be used together within the same process control network.

Regardless of the communication protocol utilized, field devices may require on-site setup, configuration, testing, and maintenance. For example, before a field device can be installed at a particular location at a process control plant, the field device may need to be programmed and may then need to be tested before and after the field device is installed. Field devices that are already installed may also need to be regularly checked for maintenance reasons or, for example, when a fault is detected and the field device needs to be diagnosed for service or repair.

Generally speaking, configuration and testing of field devices are performed on location using a handheld maintenance tool, such as a portable testing device (“PTD”). Because many field devices are installed in remote, hard-to-reach locations, it is more convenient for a user to test the installed devices in such remote locations using a PTD rather than using a full configuration and testing device, which can be heavy, bulky, and non-portable, generally requiring the installed field device to be transported to the site of the diagnostic device.

Regardless of the communication protocol utilized, field devices may require setup, configuration, testing, and maintenance. For example, before a field device can be installed at a particular location at a process control plant, the field device may need to be programmed and may then need to be tested before and after the field device is installed. Field devices that are already installed may also need to be regularly checked for maintenance reasons or, for example, when a fault is detected and the field device needs to be diagnosed for service or repair. Operators use industrial computing devices to configure, troubleshoot, calibrate, analyze and perform other operations on process control devices (e.g., controllers, field devices, etc.). In some known systems, an operator may conduct a number of analyses and/or management of a field device using a stationary industrial computing device (e.g., a personal computer, workstations, etc.) to perform asset management, vibration management, industrial computing device fleet management, etc.

On the other hand, configuration and testing of field devices may be performed on location using a portable industrial computing device, such as a handheld field communicator, calibrator, portable testing device (“PTD”), etc. An operator may physically attach the portable industrial computing device to a field device and may then communicate with the field device via the portable industrial computing device for diagnostics, to change the configuration, to calibrate the field device, etc. For example, because many field devices are installed in remote, hard-to-reach locations, it is more convenient for a user to test the installed devices in such remote locations using a PTD rather than using a full configuration and testing device, such as a stationary industrial computing device, which can be heavy, bulky, and non-portable, generally requiring the installed field device to be transported to the site of the diagnostic device.

When a user, such as a service technician, performs maintenance testing and/or communications with a field device, the PTD is typically communicatively connected to a communication link (e.g., a current loop or Fieldbus segment) or directly to a field device (e.g., via communication terminals of the field device). The PTD initially attempts to communicate with the field device, such as by sending and/or receiving digital communication signals along the loop or segment using the communication protocol supported by the field device. If the current loop or segment is in proper operating condition, the communications signals may be sent and/or received without problem. However, if the loop, segment, or field device contains an electrical fault, such as a short or a break, communications may be impeded, and it may be necessary to diagnose the loop, segment, and/or field device to identify the fault.

When such a fault is identified, a technician might need to use a variety of other tools to test the field device and/or communication link. For example, the technician may need to use a portable power supply to power an isolated field device. The technician may need to power an isolated field device, for example, when the field device loses power due to a plant-wide power outage or due to an issue with a local power supply. As another example, the technician may simply need to take a field device offline for troubleshooting in order to avoid negatively effecting other field devices and the rest of the process control system. The technician may also need to carry a multi-meter to measure the current, voltage, resistance, impedance, etc. available on a segment or loop, etc. Each of these tools can take up a fair amount of space, and may be inconvenient for a technician to carry in the field. To address this problem with carrying multiple tools, manufacturers have developed PTDs that include a power supply for providing power to a HART loop. Unfortunately, these powered PTDs are typically incapable of providing power to Fieldbus field devices. Further, typical portable power supplies and powered PTDs often fail to comply with Intrinsic Safety (IS) standards, and thus cannot be safely used in hazardous areas (e.g., environments or atmospheres that are potentially explosive due to the presence of explosive gas or dust).

Still further, if a field device is located in a hazardous area, the technician may need to verify that each of his or her tools operates in an intrinsically safe manner. Thus, when in a hazardous area, a technician's tools may need to comply with IS standards to ensure safe operation. Generally speaking, IS standards impose restrictions on electrical equipment and wiring in hazardous environments to ensure that the electrical equipment and wiring does not ignite an explosion. To comply with IS standards, electrical equipment generally needs to be designed with two core concepts in mind: energy limitation and fault tolerance. In any event, the requirement for IS compliance in some uses has led to the development of another set of field maintenance tools that may work with one of the field device protocols mentioned above, or others, but that is also IS compliant.

Likewise, as mentioned above, most process plants and other industrial settings (such as oil well drilling platforms, pumping stations, etc.) include other industrial equipment, such as rotating equipment, power generating or conversion equipment, vibration analyzer equipment, etc. that needs to be set up, configured, and maintained within the plant or industrial setting. A still further set of field maintenance tools may be needed to support this equipment, including configuring the equipment, testing the equipment, etc.

These types of industrial computing devices often need to communicate and exchange data in a secure and reliable manner, with proper authorization, and this need is rapidly increasing to support ever increasing capabilities and applications, which highlights a number of specific needs related to communications and data exchange within the process control system (i.e., in-plant) separate from the data highway of communications between a control room and process control devices. Although information technology (IT) infrastructure, such as Transmission Control Protocol/Internet Protocol (TCP/IP), authentication, Active Directory, etc., exists in these industrial settings, additional mechanisms and services are needed to provide additional security and access control authorization. Also, addition mechanisms and services are needed to support the communications, messaging, data transfer, and other capabilities of additional process control system applications.

SUMMARY

The present disclosure describes a communication architecture that provides a secure, reliable way to communicate between an external cloud, personal computers, industrial computing devices, etc. to other industrial computing devices (e.g., field communicators, PTDs, calibrators, etc.) in a process control system, process plant or other industrial settings. These communications include large data file transfer, real-time messaging, data synchronization, authentication and authorization, automated asset management data transfer, communication with a process instrument via an asset management system, and portable industrial computing device fleet management.

The communication architecture further provides security mechanisms, including additional levels of authorization beyond standard information technology security, in order to meet current and future security needs in process control systems, process plants or other industrial settings. In addition, the architecture provides many-to-many communications, file transfers, and operations among industrial computing devices. The communication architecture operates with protocol independence, such that it works with a number of different protocol and physical layer technologies, including WiFi, USB, etc. The communication architecture also operates with device type independence, such that it works with diverse stationary and portable industrial computing devices, and with application independence, such that it works with services for a wide range of software applications.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a distributed process control network located within a process plant or other industrial setting including industrial computing devices each having a platform using a communication architecture for platform-to-platform communications;

FIG. 2 is a block diagram of an exemplary process control messaging network operating in a process control system, process plant or other industrial setting;

FIG. 3 is a block diagram of an example interaction between industrial computing devices using a process control messaging system architecture;

FIG. 4 is a schematic relationship between the process control messaging architecture, access points, participating devices and process control messaging services;

FIGS. 5A and 5B are depictions of primary public interfaces and base classes defined in a process control messaging system architecture;

FIG. 6 is a depiction of exemplary common interfaces implemented by the process control messaging system architecture;

FIG. 7 is a sequence chart of an enrollment process between an industrial computing device and an enrollment server;

FIG. 8 is a sequence chart of a request/response operation between an industrial computing device and a time synchronization server;

FIG. 9 is a sequence chart of a large data transfer operation between an source and destination; and

FIG. 10 is a block diagram of an example industrial computing device schematically illustrated in FIG. 1.

DETAILED DESCRIPTION

FIG. 1 is a block and schematic diagram of an exemplary process control network 100 operating in a process control system, process plant or other industrial setting 10. The process control network 100 may include a network backbone 105 providing connectivity directly or indirectly between a variety of other devices. The network backbone 105 may include both wireless and/or wired communication channels or links. The devices coupled to the network backbone 105 include, in various embodiments, combinations of access points 72, portable industrial computing devices 112 which may be handheld or other portable computing devices, such as a laptop computer, a tablet, a hand-held smart device, a portable testing device (PTD), etc., stationary industrial computing devices 113113, such as a personal computer, workstation, etc. each having a display screen 113 as well as various other input/output devices (not shown), servers 150, etc.

As illustrated in FIG. 1, the controller 11 is connected to the field devices 15-22 via input/output (I/O) cards 26 and 28 which may implement any desired process control communication protocol, such as one or more of the HART, Fieldbus, CAN, Profibus, etc., protocols. The controller 11 is, in FIG. 1, communicatively connected to the field devices 15-22 to perform control of the field devices 15-22 and therefore control of the plant. Generally, the field devices 15-22 may be any types of devices, such as sensors, valves, transmitters, positioners, etc., while the I/O cards 26 and 28 may be any types of I/O devices conforming to any desired communication or controller protocol. For example, the field devices 15-22 and/or I/O cards 26 and 28 may be configured according to the HART protocol or to the Fieldbus protocol. The controller 11 includes a processor 30 that implements or oversees one or more process control routines 38 (or any module, block, or sub-routine thereof) stored in a memory 32. Generally speaking, the controller 11 communicates with the devices 15-22 and the host computers 113 to control a process in any desired manner. Moreover, the controller 11 implements a control strategy or scheme using what are commonly referred to as function blocks (not shown), wherein each function block is an object or other part (e.g., a subroutine) of an overall control routine that operates in conjunction with other function blocks (via communications called links) to implement process control loops within the process control system 10. Function blocks typically perform one of an input function, such as that associated with a transmitter, a sensor or other process parameter measurement device, a control function, such as that associated with a control routine that performs PID, fuzzy logic, etc. control, or an output function that controls the operation of some device, such as a valve, to perform some physical function within the process control system 10. Of course, hybrid and other types of function blocks exist and may be utilized. The function blocks may be stored in and executed by the controller 11 or other devices.

As illustrated in FIG. 1, wireless gateways 35, and wireless communication networks 70 are likewise communicatively coupled to the network backbone 105. The communication networks 70 may include wireless devices 40-58, which include wireless field devices 40-46, wireless adapters 52 a and 52 b, access points 55 a and 55 b, and a router 58. The wireless adapters 52 a and 52 b may be connected to non-wireless field devices 48 and 50, respectively. Though FIG. 1 depicts only a single one of some of the devices connected to the network backbone 105, it will be understood that each of the devices could have multiple instances on the network backbone 105 and, in fact, that the process plant 10 may include multiple network backbones 105.

The industrial computing devices 112, 113113 may be communicatively connected to the controller 11 and the wireless gateway 35 via the network backbone 105. The controller 11 may be communicatively connected to wireless field devices 40-46 via the network backbone 105 and a wireless gateway 35. The controller 11 may operate to implement a batch process or a continuous process using at least some of the field devices 15-22 and 40-50. The controller 11, which may be, by way of example, the DeltaV™ controller sold by Emerson Process Management, is communicatively connected to the process control network backbone 105. The controller 11 may be also communicatively connected to the field devices 15-22 and 40-50 using any desired hardware and software associated with, for example, standard 4-20 mA devices, I/O cards 26, 28, and/or any smart communication protocol such as the FOUNDATION® Fieldbus protocol, the HART® protocol, the Wireless HART® protocol, etc. In the embodiment illustrated in FIG. 1, the controller 11, the field devices 15-22 and the I/O cards 26, 28 are wired devices, and the field devices 40-46 are wireless field devices.

Moreover, the one or more portable industrial devices 112, which may be field device maintenance tools, multi-meters, portable loop power supplies, field device configuration tools, etc., may be intermittently communicatively connected to one or more of the field devices 15-22, 40-50 and/or to one or more of the buses or communication lines to which the field devices 15-22, 40-50 are connected (e.g., a HART loop, a Fieldbus segment, etc.), with such connections being illustrated with dotted lines in FIG. 1. Such network connections may include the hardwired lines connecting one or more of the field devices 15-22, 40-50 to the I/O cards 26 and 28 via the backbone 105, for example. Alternatively, the portable industrial devices 112 may be communicatively connected directly to ones of the field devices 15-22, 40-50 (e.g., via communication terminals present on the field devices 15-22, 40-50). In some cases, the portable industrial devices 112 may provide power to the field device 15-22, 40-50 or to the wire loop to which it is connected. Moreover, the portable industrial devices 112 may enable a user to communicate with, configure, perform maintenance activities on, and/or diagnose one or more of the field devices 15-22, 40-50 when these field devices are installed in the plant. In still other cases, the portable industrial devices 112 may include wireless interfaces that may be used to connect wirelessly to one or more of the field devices 15-22, 40-50, such as a Bluetooth interface, a Wi-Fi interface, or a wireless process control protocol interface or connection, such as those that use the WirelessHART protocol. The portable industrial devices 112 described herein are generally described for configuring, supporting, and maintaining field devices and are thus shown as field device communicators which may be used to, for example, support process measurement devices, such as pressure, temperature, level, flow analytical sensor, flow meters, valve positioners, etc. However, the portable industrial devices 112 could be used to support, connect to, maintain, communicate with, or otherwise be used with other types of devices including, for example, rotating equipment, vibration detection and analysis equipment, power generating equipment, switches, motors, pumps, compressors, drives, mechanical vessels, such as tanks, pipes, etc., electrical power distribution devices, switch gear, motor control centers any other stand-alone equipment (e.g., equipment not communicatively connected to a process controller, for example), or any other types of industrial equipment. In these cases, the portable industrial devices 112 could have various different types of communication and electrical generation and detection hardware (e.g., voltage, current, impedance, etc. generation and detection equipment) to perform maintenance on, configuration of, and/or communication with these other types of industrial equipment.

In some embodiments, the portable industrial computing device 112 may be brought to the site of one of the field devices 15-22, 40-50 in the process plant. The portable industrial computing device 112 may be temporarily connected via a wired and/or a wireless connection to the field device 15-22, 40-50 for calibrating, configuring, troubleshooting, monitoring, controlling, or performing any other suitable operations on the field device 15-22, 40-50. Additionally, the portable industrial computing device 112 may be temporarily connected via a wired and/or wireless connection to the controller 11 for calibrating, configuring, troubleshooting, monitoring, controlling, or performing any other suitable operations on the controller 11.

In operation of the industrial computing devices 112, 113, the industrial computing devices 112, 113 may, in some embodiments, each execute a user interface (UI), allowing the industrial computing device 112, 113 to accept input via an input interface and provide output at a display. The industrial computing device 112, 113 may receive data (e.g., process related data such as process parameters, permissions, log data, sensor data, and/or any other data that may be captured and stored) from the server 150. In other embodiments, the UI may be executed, in whole or in part, at the server 150, where the server 150 may transmit display data to the industrial computing device 112, 113. The industrial computing device 112, 113 may receive user interface data (which may include display data and permission data) via the backbone 105 from other nodes or endpoints in the process control network 100, such as the controller 11, the wireless gateway 35, other industrial computing devices, or the server 150.

In some embodiments, permissions may be generated at the server 150 by a system administrator, for example, as part of a registration process for each industrial computing device 112. Each permission may specify a level of access to a particular process control device, such as read-only access, read/write access, access for calibration functions, access for configuration functions, etc. The system administrator may also assign permissions to users and industrial computing devices 112, 113 in the process plant. In some embodiments, the server 150 may be communicatively coupled to one or more databases which store indications of the permissions, authorized users within the process plant, industrial computing devices within the process plant, and associations between the permissions, users, and industrial computing devices. The permissions as well as indications of the corresponding users and industrial computing devices assigned to each permission may be transmitted to the industrial computing device 112, 113.

Accordingly, the industrial computing device 112, 113 may determine a level of authorization that the user has to a process control device connected to the industrial computing device 112, 113 using the permissions assigned to the user and/or the industrial computing device 112, 113 as part of registering the device 112, 113 with the process control network 100. As used herein, a level of authorization for a user may refer to a combined level of access that the user has to process control devices within the process plant. The combined level of access may be based on a set of permissions assigned to the user and/or the industrial computing device 112, where each permission specifies a level of access to a particular process control device. In some embodiments, a level of authorization for a user may also refer to a combined level of access that the user has to a particular process control device. The combined level of access may be based on each of the permissions assigned to the user and/or the industrial computing device 112, 113 which specify a level of access to the particular process control device.

Based on user data received at the industrial computing device 112, 113, the industrial computing device 112, 113 provides output (i.e., visual representations or graphics) indicating whether the user is authenticated and whether the user is authorized to access a particular process control device or function performed on the process control device. For example, the industrial computing device 112, 113 may provide an ID scan display requesting the user to scan an electronic ID card. The industrial computing device 112, 113 may also provide a user login display requesting the user to enter a username and password. The user may also affect control of the process by providing input at the industrial computing device 112, 113. For example, the portable industrial computing device 112 may provide indications of process parameters measured by a process control device which is connected to the portable industrial computing device 112. The user may interact with the portable industrial computing device 112 to calibrate the measurements taken by the process control device.

In certain embodiments, the industrial computing device 112, 113 may implement any type of client, such as a thin client, web client, or thick client. For example, the industrial computing device 112, 113 may depend on other nodes, computers, industrial computing devices, or servers for the bulk of the processing necessary for operation of the industrial computing device 112, 113, as might be the case if the industrial computing device is limited in memory, battery power, etc. (e.g., in a wearable device). In such an example, the industrial computing device 112, 113 may communicate with the server 150 or with another industrial computing device, where the server 150 or other industrial computing device may communicate with one or more other nodes (e.g., servers) on the process control network 100 and may determine the display data, permissions data, and/or process data to transmit to the industrial computing device 112, 113. Furthermore, the industrial computing device 112, 113 may pass any data related to received user input to the server 150 so that the server 150 may process the data related to user input and operate accordingly. In other words, the industrial computing device 112, 113 may do little more than render graphics and act as a portal to one or more nodes or servers that store the data and execute the routines necessary for operation of the industrial computing device 112, 113. A thin client industrial computing device offers the advantage of minimal hardware requirements for the industrial computing device 112, 113.

In other embodiments, the industrial computing device 112, 113 may be a web client. In such an embodiment, a user of the industrial computing device 112, 113 may interact with the process control system via a browser at the industrial computing device 112, 113. The browser enables the user to access data and resources at another node or server (such as the server 150) via the backbone 105. For example, the browser may receive data, such as display data, permissions data, or process parameter data from the server 150, allowing the browser to depict graphics for controlling and/or monitoring some or all of the process. The browser may also receive user input (such as a mouse click on a graphic). The user input may cause the browser to retrieve or access an information resource stored on the server 150. For example, the mouse click may cause the browser to retrieve (from the server 150) and display information pertaining to the clicked graphic.

In yet other embodiments, the bulk of the processing for the industrial computing device 112, 113 may take place at the industrial computing device 112, 113. For example, the industrial computing device 112, 113 may determine a level of authorization for the user. The industrial computing device 112, 113 may also store, access, and analyze data locally.

In operation, a user may interact with the industrial computing device 112, 113 to analyze, monitor, configure, troubleshoot, calibrate, or control one or more devices in the process control network 100, such as any of the field devices 15-22, 40-50 or the controller 11. The user may also interact with the portable industrial computing device 112, for example, to modify or change a parameter associated with a control routine stored in the controller 11. The processor 30 of the controller 11 implements or oversees one or more process control routines (stored in the memory 32), which may include control loops. The processor 30 may communicate with the field devices 15-22 and 40-50 and with other nodes that are communicatively connected to the backbone 105. It should be noted that any control routines or modules (including quality prediction and fault detection modules or function blocks) described herein may have parts thereof implemented or executed by different controllers or other devices if so desired. Likewise, the control routines or modules described herein which are to be implemented within the process control system may take any form, including software, firmware, hardware, etc. Control routines may be implemented in any desired software format, such as using object oriented programming, ladder logic, sequential function charts, function block diagrams, or using any other software programming language or design paradigm. In particular, the control routines may be implemented by a user through the industrial computing device 112, 113. The control routines may be stored in any desired type of memory, such as random access memory (RAM), or read only memory (ROM). Likewise, the control routines may be hard-coded into, for example, one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware elements. Thus, the controller 11 may be configured (by a user using an industrial computing device 112, 113 in certain embodiments) to implement a control strategy or control routine in any desired manner.

Referring still to FIG. 1, the wireless field devices 40-46 communicate in a wireless network 70 using a wireless protocol, such as the Wireless HART protocol. In certain embodiments, the industrial computing device 112, 113 may be capable of communicating with the wireless field devices 40-46 using the wireless network 70. Such wireless field devices 40-46 may directly communicate with one or more other nodes of the process control network 100 that are also configured to communicate wirelessly (using the wireless protocol, for example). To communicate with one or more other nodes that are not configured to communicate wirelessly, the wireless field devices 40-46 may utilize a wireless gateway 35 connected to the backbone 105. Of course, the field devices 15-22 and 40-46 could conform to any other desired standard(s) or protocols, such as any wired or wireless protocols, including any standards or protocols developed in the future.

The wireless gateway 35 is an example of a provider device that may provide access to various wireless devices 40-58 of a wireless communication network 70. In particular, the wireless gateway 35 provides communicative coupling between the wireless devices 40-58 and other nodes of the process control network 100 (including the controller 11 of FIG. 1A). The wireless gateway 35 provides communicative coupling, in some cases, by the routing, buffering, and timing services to lower layers of the wired and wireless protocol stacks (e.g., address conversion, routing, packet segmentation, prioritization, etc.) while tunneling a shared layer or layers of the wired and wireless protocol stacks. In other cases, the wireless gateway 35 may translate commands between wired and wireless protocols that do not share any protocol layers.

Similar to the wired field devices 15-22, the wireless field devices 40-46 of the wireless network 70 may perform physical control functions within the process plant 10 (e.g., opening or closing valves or taking measurements of process parameters). The wireless field devices 40-46, however, are configured to communicate using the wireless communication protocol of the network 70, whereas the wired field device 15-22 are configured to communicate using a wired communication protocol (e.g., HART®, FOUNDATION® Fieldbus, etc.). As such, the wireless field devices 40-46, the wireless gateway, and other wireless nodes 52-58 of the wireless network 70 are producers and consumers of wireless communication packets, whereas the wired field devices 15-22 are producers and consumers of wired communication packets.

In some scenarios, the wireless network 70 may include non-wireless devices. For example, a field device 48 of FIG. 1A may be a legacy 4-20 mA device and a field device 50 may be a traditional wired HART device. To communicate within the network 70, the field devices 48 and 50 may be connected to the wireless communication network 70 via a wireless adaptor 52 a or 52 b. Additionally, the wireless adaptors 52 a, 52 b may support other communication protocols such as FOUNDATION® Fieldbus, PROFIBUS, DeviceNet, etc. Furthermore, the wireless network 70 may include one or more network access points 55 a, 55 b, which may be separate physical devices in wired communication with the wireless gateway 35 or may be provided with the wireless gateway 35 as an integral device. The wireless network 70 may also include one or more routers 58 to forward packets from one wireless device to another wireless device within the wireless communication network 70. The wireless devices 32-46 and 52-58 may communicate with each other and with the wireless gateway 35 over wireless links 60 of the wireless communication network 70.

In certain embodiments, the process control network 100 may include other nodes connected to the network backbone 105 that communicate using other wireless protocols. For example, the process control network 100 may include one or more wireless access points 72 that utilize other wireless protocols, such as WiFi or other IEEE 802.11 compliant wireless local area network protocols, mobile communication protocols such as WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution) or other ITU-R (International Telecommunication Union Radiocommunication Sector) compatible protocols, short-wavelength radio communications such as near field communications (NFC) and Bluetooth, or other wireless communication protocols. Typically, such wireless access points 72 allow handheld or other portable computing devices (e.g., portable industrial computing devices 112) to communicate over a respective wireless network that is different from the wireless network 70 and that supports a different wireless protocol than the wireless network 70. For example, a portable industrial computing device 112 may be a mobile workstation or diagnostic test equipment that is utilized by a user within the process plant. In some embodiments, the industrial computing device 112, 113 communicates over the process control network 100 using a wireless access point 72. In some scenarios, in addition to portable computing devices, one or more process control devices (e.g., controller 11, wired field devices 15-22, or wireless devices 35, 40-58) may also communicate using the wireless network supported by the access points 72.

Although FIG. 1 illustrates a single controller 11 with a finite number of field devices 15-22, 40-50, this is only an illustrative and a non-limiting embodiment. Any number of controllers 11 may be included in the provider devices of the process control network 100, and any of the controllers 11 may communicate with any number of wired or wireless field devices 15-22, 40-50 to control a process in the plant 10. Furthermore, the process plant 10 may also include any number of wireless gateways 35, routers 58, access points 55, 72, portable industrial computing devices 112, stationary industrial computing devices 113, and/or wireless process control communication networks 70.

In some embodiments the server 150 may act as an enrollment server for registering and enrolling industrial computing devices 112, 113 in a process control messaging service. That is, where the process control network 100 may permit communication between various industrial computing devices 112, 113, servers 150, etc., a process control messaging network may be logically separate from the process control network 100 to permit intercommunication among and between industrial computing devices 112, 113 using a process control messaging service. The process control messaging service is a grouping of infrastructural services and capabilities deployed in a distributed manner on the physical process control network 100, but logically separate from the digital process control communication channel or link used for communications between the controller 11 and the field devices 15-52. The process control messaging service provides secure, reliable, fast/responsive communications, message delivery, data transfer and other operations between IT systems, personal computer and industrial devices 112, 113. In doing so, the process control messaging service enables a number of other networked capabilities including, but not limited to, communication between an industrial computing device 112, 113 and a field device 15-50 via an asset management system, data synchronization between an industrial computing device 112, 113 and an asset management system, field device access control from an industrial computing device 112, 113, and fleet management of industrial computing devices 112, 113, particularly portable industrial computing devices 112. The process control messaging service does not replace other IT network and security systems and services, but extends those IT capabilities and provides another layer of security/authorization, services and capabilities that are applicable to the types of application capabilities needed in a process control system.

FIG. 2 is a block diagram of an exemplary process control messaging network 200 operating in a process control system or process plant 10 (or other industrial setting or environment). In particular, the process control messaging network 200 may include a variety of portable industrial computing devices 112 a-112 e, such as laptop computers, tablets and hand-held field communicators, and a variety of stationary industrial devices 113 a-113 c, such as personal computers and workstations. The various industrial computing devices 112 a-112 e, 113 a-113 c may be connected directly or indirectly via one or more network backbones 202, 204, 206. Each backbone 202-206 may correspond to different network levels within the process control system. For example, the plant network and communication system 10 additionally includes a set of interconnected communication networks at the plant site (or at multiple plant sites or locations). In particular, the plant networks illustrated in FIG. 2 include a top level or business network 202, a plant administrative network 203, and a plant device network 204 which is connected to one or more control networks 206 (only one of which is illustrated in FIG. 2). As will be understood, the plant network 204 and the control network 206 may be the network 105 and sub-networks connected thereto for supporting the field devices 15-50 illustrated in FIG. 1. The process control messaging network 200 includes or is connected to an external server network 210 which may be located at an external (to the plant or other industrial setting) site, such as in the cloud.

As illustrated in FIG. 2, the business network 202 includes a set of business computers, workstations or other business stationary industrial computing devices 113 a-113 c which may implement business, accounting, planning, etc. applications, and this network 202 is connected to the external server system or network 210 via a firewall device 230. Likewise, the business network 202 is connected to the administrative network 203 and to the plant network 204 via a DMZ device or system 240 which acts as a network-to-network intermediary. Generally speaking the business network 202 includes several workstations 113 a-113 c connected to a communication link 242 consistent with any suitable communication standard such as the IEEE 802.3 Ethernet standard, for example. As is typical, the workstations 113 a-113 c share an operating system having networking capabilities such as, for example, Windows™ manufactured by the Microsoft Corporation. Users in various organizational roles operate the workstations 113 a-113 c to carry out day-to-day activities within the plant, such as that of a plant operator, business systems that manage the plant, etc. For example, the plant operator may employ engineers, accountants, marketing staff, and other personnel. Users who operate the workstations 113 a-113 c may have a certain set of permissions that typically do not permit these users to access the process plant network 204 or the process control network 206. On the other hand, these users have a mostly unrestricted access to hosts on the Internet and, as a result, a relatively high risk of exposure to viruses, malware, hijacking attempts, and other cyber threats.

Likewise, the administrative network 203 includes various computers or workstations connected via a communication link 244 consistent with any suitable communication standard such as the IEEE 802.3 Ethernet standard, for example. One or more of the personal computers, workstations, or other stationary industrial computing devices illustrated as a workstation 246 in FIG. 2, may operate as a fleet management station which includes or is connected to a local content repository 247 which stores local content for various of the portable industrial computing devices in the plant. Likewise, the administrative network 203 may include one or more process control messaging network access points 208 a which may be wireless access points that enable one or more portable industrial computing devices 112 a-112 c (each having a wireless interface) to connect to the network 203 in a wireless manner, and thus to connect to the workstation 246 for large file transfers, messaging, etc., as will be described in more detail herein.

In a similar manner, the plant network 204, which may be the network 100 of FIG. 1, includes various computers or workstations 260, data historians 262, etc. which are examples of stationary assets or devices connected via a communication link 264 consistent with any suitable communication standard such as the IEEE 802.3 Ethernet protocol, for example. The network 204 is connected via an access point 266, which may be a firewall or a control device, for example, to the process control network 206. Generally speaking, the workstations 260 may be operator workstations that enable process or control operators to view and control ongoing operations of the devices in the process control network 206 (such as controllers, field devices, etc.) to perform plant or on-line control operations. These workstations 260 may include and execute various different applications that enable personnel such as operators and maintenance personnel to perform various analyses on control assets, such as field devices, and on other types of assets, such as rotating equipment, vibration equipment, power generation equipment, etc. As illustrated in FIG. 2, one or more of the stationary industrial computing devices, illustrated as a workstation 268, may operate as a fleet management station which includes or is connected to a local content repository 270 that stores local content for various ones of portable industrial computing devices 112 d-112 f in the plant. If desired, the workstation 268 may operate to manage and the local content repository 270 may store local content for various ones of the stationary industrial computing devices as well or instead. Likewise, the plant network 204 may include one or more process control messaging network access points 208 b which may be wireless access points that enable one or more of the portable industrial computing devices 112 d-112 f (each having a wireless communication interface) to connect to the network 204 and thus to the workstation 268 for large file transfers, messaging, etc., as will be described in more detail herein. The portable industrial computing devices 112 a-112 f may include multiple devices of the same type (e.g., field communicators, oscilloscopes, ammeters, etc.) and may include devices of different types as well as devices made by different manufacturers or devices having different capabilities.

As will be understood, the control network 206 may include various control devices and sub-networks, such as controllers, input/output (I/O) devices, and field devices connected via proprietary or process control networks such as HART, FOUNDATION Fieldbus, Profibus, CAN, etc. networks, and these sub-networks may use any desired process control protocol. Generally speaking, the portable industrial computing devices 112 a-112 f may be used to perform maintenance, checkout, repair, testing, calibration, and configuration activities on these devices and sub-networks. Likewise, the plant or other industrial setting may include other types of devices, such as vibration analysis and monitoring devices, rotating equipment, power generation equipment, etc. disposed therein that is not illustrated in FIG. 2 but that may be serviced, maintained, installed, repaired, tested, calibrated, etc. using one or more portable industrial computing devices 112 a-112 f.

In addition, combinations of process control messaging access points 208 a-208 c may be distributed on each network 202-206 for connectivity directly or indirectly between industrial computing devices 112 a-112 e, 113 a-113 c, 246, 268 to access (i.e., register and/or enroll in) the process control messaging network 200, and, in turn, access process control messaging services. Generally speaking, these access points 208 a-208 c are at least logically separate from the access points 55 a, 55 b and the wireless gateway 35, and in some embodiments are both logically separate and physically separate from the access points 55 a, 55 b and the wireless gateway 35. In other words, in some embodiments the access points 208 a-208 c may utilize the same hardware as the access points 55 a, 55 b and the wireless gateway 35, though in other embodiments the access points 208 a-208 c have their own hardware separate from the access points 55 a, 55 b and/or the wireless gateway 35. As with FIG. 1, although FIG. 2 depicts only single ones of some of the devices connected to the network backbones 202-206, it will be understood that each of the devices could have multiple instances on the network backbones 202-206 and, in fact, that the process plant 10 may include multiple network backbones 202-206 for each network level.

The DMZ layer or device 240 operates to separate the process control layers or networks 204 and 206 as well as the plant or industrial setting device networks, and the administrative network 203 from the internet or other external networks or public networks, such as the business LAN network 202 and the external network 210. In the example communication system 10 of FIG. 2, the plant LAN layer or business network 202 is connected to the internet or other public network via a router/firewall 230, and the plant DMZ layer 240 is connected to the plant LAN layer or business network 200 via a router/firewall as part of the DMZ 240.

The plant DMZ 240 may include several servers such as an anti-virus server, a data server, and a historian server. As is known, a DMZ layer 240 generally provides additional security to a local or plant networks, such as the networks 203, 204, and 206, by limiting direct exposure to a larger network such as the internet to only several hosts (i.e., the anti-virus server, data server and historian server, a DNS server, a web server, etc.). It will be noted that the DMZ layer or device 240 in general may be any intermediate network layer that improves the security of the systems 203, 204, and 206 by directing all incoming and outgoing internet traffic via one or several hosts that implement security features to make the communications secured. In addition to the process control messaging network 200 within the process control system or process plant 10, the process control messaging network 200 may be communicatively coupled to a computing cloud or other system external 210 to the process control system 10, where the external system 210 includes its own IT systems, infrastructure, etc. including its own servers 212. In some embodiments, the external system 210 may provide storage, analysis and/or updating services as a third part to the process control system 10. For example, the external system 210 may maintain information on the configuration of the process control system 10, including uploading information on the configuration, diagnostics, etc. of specific field devices 15-52 from individual ones of the industrial computing devices 112 a-112 e, 113 a-113 c, 246, 268 content downloads to the industrial computing devices 112 a-112 e, 113 a-113 c 246, 268 en masse or to individual ones of the industrial computing devices, license management, etc.

Moreover, the external system 210 of FIG. 2 includes various systems and components, such as, for example, an end-user repository 290, a notifier 292, a content decider 294, and a content downloader 296 which may generally operate together to determine the content that needs to be downloaded to various ones of the industrial computing devices 112 a-112 e, 113 a-113 c, 246, 268. The system 210 may also include one or more business systems or computers 299. The business systems 299 may be used to purchase or acquire new content for one or more of the portable devices 112 a-112 e, 113 a-113 c, 246, 248, and may provide indications of such a purchase or license in the form of license keys, codes, etc. Likewise, the various firewall and DMZ devices 230 and 240 include programing or configurations that enable secure communications between the industrial computing devices and the components in the external network 210. For example, the workstations 246 and 268 include communications software that enable these devices to navigate the DMZ and firewall devices 230 and 240 to communicate through these devices in a secured manner to the external network 210.

More specifically, the portable industrial computing devices 112 a-112 e may include field communicators, calibrators, and other types of portable devices, that are used in industrial settings such as industrial plants, process plants, oil wells, pumping stations, etc., to configure, troubleshoot, calibrate, and perform other operations on field devices such as process measurement devices, valves, positioners, etc. as well as other types of devices or assets used in industrial settings, such as rotating equipment (turbines for example), power generation equipment, vibration analysis and detection equipment, etc. Of course, different types and brands of industrial portable devices may be manufactured by the same or different manufacturers, and various ones of the portable industrial computing devices 112 a-112 e may have different features and capabilities. For example, some of the portable industrial computing devices 112 a-112 e may be field communicators that communicate on one or more of the various sub-networks 206 in the plant to communicate with field devices such as HART or Fieldbus field devices. Some of the portable industrial computing devices 112 a-112 e may be calibrators or configurators that calibrate or configure devices in the plant, including field devices and other types of devices, such as rotating equipment, vibration analyzers, etc. Still further, some of the portable industrial computing devices 112 a-112 e may be or may include electrical testing functionality, such as ammeters, voltmeters, resistance meters, impedance meters, or multi-meters used to test wiring and other devices in the plant, such as power supplies. Likewise, some of the portable industrial computing devices 112 a-112 e may be intrinsically safe and thus able to be used in hazardous environments. Some of the portable industrial computing devices 112 a-112 e may be specially configured portable devices made by various manufacturers, or may be implemented as software features or hardware implemented on or connected to a general purpose computer, such as a laptop, a phone, a personal digital assistant (PDA), a tablet computer, etc. The portable industrial computing devices 112 a-112 e may be grouped into one or more fleets of portable devices in any manner using, for example, one of the workstations 246, 268 as fleet management stations, based on, for example, functionality, use, type, manufacturer, users, etc., or any combination of these and other characteristics. In order to provide additional security above and beyond standard IT security mechanisms (e.g., user authentication, Active Directory, etc.), the process control messaging network 200 maintains network isolation between external networks, such as the external cloud 210, and internal communication networks at the end user's site (e.g., the plant) typically include multiple, isolated networks, including business networks 202, plant networks 204, control networks 206, etc., and a network-to-network intermediary or DMZ device 240 executes software that runs on top of the existing routers in the plant to interconnect these networks. In one example, the DMZ software implements port re-direction which retains network isolation, but allows the computers or industrial devices on a plant network to gain secure access to other networks including the external cloud network 210. Thus, while process control messaging network 200 may include much of the same or similar hardware as the process control network 100, the process control messaging network 200 remains logically separate from the process control network 100. At the same time, the process control messaging access points 208 a-208 c distributed among the multiple, isolation networks and the process control messaging service permit communication across multiple, isolated networks. As used herein, the networks 202, 203, 204, 206 and the devices connected thereto may be considered to be all at the same general location referred to as a first or a second location, or these networks and devices may be considered to be at different locations.

Additionally, the feet management stations 246 and 268 are computers or workstations having processors that execute associated fleet management software that are, in this example, located at the end user's site or in the plant. These devices are used as the user interface by a plant or fleet administrator, for example, to manage each of the identified fleets of portable industrial computing devices in the plant. More particularly, these computers are used by the portable (or stationary) device fleet administrator to perform some or all activities in conjunction with automatically and semi-automatically managing the content within the fleets of industrial portable devices 112 a-112 f as well as fleets of stationary devices if so desired. Likewise, the local content repositories 247 and 270 are databases that locally store content for the portable industrial computing devices 112 a-112 f (as well as for stationary devices if desired) at the end-user's site prior to or after that content has been downloaded to the various portable industrial computing devices 112 a-112 f or stationary devices 113 a-113 c.

However, in at least one embodiment such as that illustrated in FIG. 2, the external cloud or server system (IT systems, infrastructure, etc.) that is external to the plant networks includes the content decider 294 which is a software mechanism that generally runs on IT infrastructure (servers, processors, etc.) in the external cloud to evaluate a number of different input criteria, and to determine what filtered/targeted content a particular industrial portable device (or content that a particular stationary device) at a particular customer site is entitled to have or use. Generally speaking, the content decider 294 stores or receives inputs detailing the features, programming, operating systems, upgrades, etc. (all of which is referred to as content), and configuration information indicating configuration parameters for the industrial portable devices 112 a-112 f or stationary devices, and determines what content each industrial device in the fleet of industrial portable devices or stationary devices is allowed to have. Moreover, the content downloader 296 is coupled to the content decider 294 and provides efficient, secure connections for downloading content to the industrial devices, as specified by the content decider 294, via the external and internal networks of the plant in which the industrial portable device or stationary device is used or located.

Still further, the source content repository 298 stores all content available for download to the industrial portable devices 112 a-112 f (or stationary devices if so desired) and provides that content to the content downloader 296 when needed to be downloaded to the industrial portable devices 112 a-112 f (or stationary devices) in the plant. The notifier 292 is a module (e.g., software executed on a processor) that sends notifications to users when content becomes available for or is determined to be downloadable to particular industrial devices, such as when the content decider 294 determines that new content has been obtained (e.g., licensed or purchased) using one of the business systems computers 299. Generally speaking, the business systems computers 299 include user account and authentication, purchasing, order management systems, an application or feature store, etc., that may be used to acquire new content. Finally, the end user information repository 290 is a database and communication module that gathers and stores end-user information regarding or detailing the current list of content and versions of such content on each industrial portable device in the fleet of industrial portable devices 112 a-112 f and/or on each a set of stationary devices in a fleet of stationary devices in a plant or other industrial setting.

FIG. 3 illustrates a block diagram of an example interaction between a requesting endpoint (RequestEndpoint) and a responding endpoint (ResponseEndpoint), such as between industrial computing devices 112, 113 using a process control messaging system architecture 300. In one example, the firewalls 230 and/or the DMZ 240 act as endpoints, and, more particularly, intermediary endpoints, for redirecting messages from a requesting endpoint to a responding endpoint across networks. As mentioned, the DMZ software implements port re-direction which retains network isolation, but allows industrial computing devices to gain secure access to other networks and communicate with other industrial computing devices or with external networks. As such, a requesting endpoint may specify the firewall or DMZ as an endpoint, with information in the request specifying the responding endpoint in the other network. The firewall or DMZ may receive the message, and, using security software, analyze and/or scrub the message for redirection to the responding endpoint using port redirection.

Each endpoint includes a platform and an application. The interaction can be broken down into registration, enrollment and participation in the process control messaging service. It should be understood from the following that the process control messaging system architecture 300 is platform independent, such that it enables communication between a variety of platforms, including, but not limited to, other industrial device computing platforms (e.g., operating systems and interfaces such as Windows XP, Windows Embedded Compact 2013, Windows 10, etc.), and field device communication platforms (e.g., Fieldbus, HART, etc.).

Further, the process control messaging system architecture 300 enables specifying transport types/protocol independence at the physical layer (e.g., WiFi, Universal Serial Bus (USB), etc.) for a particular application based on best protocol fit. For example, a portable industrial computing device 112 a using the process control messaging system architecture 300 may specify a WiFi transport type when connecting to the process control messaging service via a wireless access point 208 a, whereas the portable industrial computing device 112 a may specify a USB transport type when connecting to the process control messaging service via a USB connection to a personal computer 112 b.

In particular, the process control messaging system architecture 300 includes components and services, which are deployed on individual industrial computing devices 112, 113, and centralized computers, such as the server 150. The components and services of the process control messaging system architecture 300 are represented as a layer of abstraction having a dedicated communication protocol above standard IT infrastructure and services (e.g., TCP/IP, authentication, Active Directory), and particularly above the transport layer of the process control network. Thus, where the transport layer has a network communication protocol corresponding to the process control network (e.g., TCP/IP), the communication protocol of the process control messaging service is layered above the network communication protocol.

The process control messaging system architecture 300 further includes a process control communication protocol (e.g., Fieldbus, HART, etc.) layered above the communication protocol of the process control messaging service. As such, a requesting industrial computing device may specify the communication protocol of the destination device, be it another industrial computing device, a field device, etc.

Generally speaking, the process control messaging system architecture 300 facilitates request-response and large data transfer operations between machine platforms connected via wireless or wired connection within the plant infrastructure. The process control messaging system architecture 300 is designed to support various activities for services within the plant or other industrial setting such as exchanging information between services within the external network or cloud 210 (e.g., licensing and updating services for industrial computing devices, web services (e.g., web extender client), etc.) and platforms connected to the process control messaging network 200 (e.g., internal plant services, which essentially comprises enrolled platforms that provide services in the multi-platform environment). Each platform may include multiple instances of the process control messaging architecture installed and running on the system of the platform (e.g., industrial computing devices). On the other hand, a simple implementation would have one computing device (e.g., a stationary industrial computing device) with a single instance of the process control messaging architecture installed, thereby having the one computing device facilitating as a connection point to services within the plant 10 or the external network 210.

In a request-response type of operation, the process control messaging system architecture supports the sending of a request to a platform endpoint, and an application-topic responding by sending the response to a specified endpoint in the request. Request and response activities involve sending and receiving data to and from endpoints referred to as “RequestEndPoint” and “ResponseEndPoint”. The RequestEndPoint is the destination to which the request is delivered and the source/origin of the response, and ResponseEndPoint is the destination to which the response is delivered and the source/origin of the request. The RequestEndPoint and ResponseEndPoint include a Platform and Application. The request-response endpoint is made up of a topic, an application and a platform. In short, the request/response operation involves a client sending a request (Topic) to an application running on a platform, and having a response returned. The topics are hosted in an application running on a platform. The topic identifies the topic for which the application should perform, with the topic name being unique across all topics within the application namespace. The application is the container which received topics and routes the topics for processing. The platform has a process which hosts the application. Therefore, in order to reach a specific topic, the request-response message specifies the application, platform and topic identifiers.

In a large data transfer (LDT) operation, the process control messaging architecture supports the transferring of files from a source location to a destination, referred to as “LDTSource” and “LDTDestination”, respectively. The LTD endpoint includes a PlatformID, which specifies the source platform and the destination platform. The LDT source and destination includes a Uniform Resource Locator (URL). The LDTSource specifies a specific resource, whereas the LDTDestination need only specify location.

In either the request/response type of operation (e.g., instant/real-time messaging, time synchronization) or the LDT operation, the request may specify quality of service in the communication between endpoints. For example, the request may specify guaranteed delivery, whereby a copy of the message is temporarily persisted in a database or other origination client storage while ascertaining the ability of the endpoint client to receive the message by acknowledging receipt, at which point the copy of the message is erased from the database. On the other hand, the request may not specify guaranteed delivery (or specify no guaranteed deliver), and send the request without persisting the message and without ascertaining the endpoint's ability to receive the message. While any operation may utilize guaranteed or unguaranteed delivery, generally speaking, large data transfer utilize guaranteed delivery due to the size of the transfer of data, whereas a request/response service, such as realtime or instant messaging, may be more concerned with the timeliness of the delivery and abstain from using guaranteed delivery.

FIG. 4 depicts a schematic relationship between the process control messaging architecture 300, access points 302, 306, participating devices or endpoints 304, 308 and process control messaging services 310-316. Using the process control messaging system architecture 300 distributed throughout devices in the process control messaging network, a variety of process control messaging services 310-316 may be provided between and among field devices 304, industrial computing devices, external clouds, personal computers 308, etc., including, but not limited to, secure communications, instant/real-time messaging, file transfer, data synchronization, time synchronization, industrial computing device platform updates. However, in order for any device, and particularly portable industrial computing devices 112, to participate in the process control messaging services and utilize services that enable communications, messaging, data transfer and other interactions with other industrial computing devices in the process control messaging network, industrial computing devices must be registered and enrolled with the process control messaging service.

Public interface definitions for the process control messaging system architecture 300 are used by applications or services to perform various activities. FIGS. 5A and 5B depict examples of primary public interfaces and base classes defined in the process control messaging system architecture 300. As shown in FIG. 5A, an example interface (IRequestSender) facilitates requests based on an Application-Topic from one platform to another, using a number or class of defined methods (RequestSenderBase). The RequestSenderBase is an abstract class implementing the IRequestSender interface that is defined in the process control messaging system architecture 300 level, and is aware of the infrastructure (e.g., messaging) of the process control messaging system architecture 300. Each request sender inherits from the base class.

In the present example, the defined methods include, but are not limited to, BeginRequest, EndRequest, PauseRequest, ResumeRequest and CancelRequest. The BeginRequest is an asynchronous method called by the requesting client (ResponseEndpoint) to start a request based on an Application-Topic to be delivered to a RequestEndpoint. The BeginRequest method utilizes an operation request specifier that contains the details of the request, an asynchronous callback to be called when the operation is complete, and a user-provided object that distinguishes each particular asynchronous operation request from other requests. The BeginRequest method returns an IAsyncOperation that represents the asynchronous operation, which, at the time, could still be pending.

The EndRequest method is a method the requesting client calls upon completion of the request to read the completion result. The EndRequest method otherwise waits for the pending asynchronous operation to complete, and utilizes the reference to the pending asynchronous request to finish which is returned by the BeginRequest method when the asynchronous operation is started, IAsyncOperation. The EndRequest method further returns the result of the asynchronous operation. The PauseRequest method is a method the requesting client calls to pause a specified asynchronous operation. The PauseRequest method utilizes the reference to the pending asynchronous request to pause as returned by the BeginRequest method when the asynchronous operation is started, IAsyncOperation. The ResumeRequest method is a method the client endpoint calls to resume a paused specified asynchronous operation. The ResumeRequest method likewise utilizes the reference to the pending asynchronous request to resume as returned by the BeginRequest method when the asynchronous operation is started, IAsyncOperation. The Cancel Request method is a method the requesting client calls to cancel a specified asynchronous operation, and utilizes the reference to the pending asynchronous request to cancel which was returned by the BeginRequest method when the asynchronous operation is started, IAsyncOperation.

As shown in FIG. 5B, an example interface (RequestReceiver) processes responses based on an Application-Topic from one platform to another, using a number or class of defined methods (RequestReceiverBase). The RequestReceiverBase is an abstract class defining or implementing the RequestReceiver interface method and is defined in the process control messaging system architecture 300 level, and is aware of the infrastructure (e.g., messaging) of the process control messaging system architecture 300. Each request receiver inherits from the base class, and implements the abstract methods.

In the present example, the defined methods include, but are not limited to, ProcessRequest, ProcessPausing, ProcessResuming, ProcessCancellation, SendResponse and NotifyStateChanged. The ProcessRequest is an abstract method (i.e., a method that is declared but contains no implementation—may not be instantiated—and requires a subclass to provide implementations) called by the receiving client (RequestEndpoint) to process an incoming request based on an Application-Topic. The ProcessRequest method utilizes the operation request specifier from the IRequestSender.BeginRequest method, IAsyncOperation, and calls upon the SendResponse method once the operation is complete. The ProcessPausing method is an abstract method called by the receiving client to process an incoming pausing request for the operation from the IRequestSender.PauseRequest method. The ProcessPausing method utilizes the operation request specifier from the IRequestSender.BeginRequest method, IAsyncOperation, to specify the operation to pause. The ProcessResuming method is an abstract method called by the receiving client to process an incoming resume request for the operation from the IRequestSender.ResumeRequest method. The ProcessResuming method utilizes the operation request specifier from the IRequestSender.BeginRequest method, IAsyncOperation, to specify the operation to resume. The ProcessCancellation method is an abstract method called by the receiving endpoint to process an incoming cancellation request for the operation from the IRequestSender.CancelRequest method. The ProcessCancellation method utilizes the operation request specifier from the IRequestSender.BeginRequest method, IAsynchOperation, to specify the operation to cancel. The ProcessCancellation method may call upon the SendResponse method when the operation is cancelled. The SendResponse method is an abstract method called by the receiving client to send the response to the ResponseEndpoint specified in the request specifier from the IRequestSender.BeginRequest method, IAsynchOperation. The SendResponse method utilizes the request specifier identification, the operation status and the operation result as part of the response. The NotifyStateChanged method is an abstract method called by the receiving client to send a change of state notification to the ResponseEndpoint specified in the request specifier from the IRequestSender.BeginRequest method, IAsynchOperation.

Referring again to FIG. 5A, the example interface (ILargeDataTransfer) facilitates large data transfers from one platform to another using a number or class of defined methods (TransferRequestSender). The TransferRequestSender implements the interface ILargeDataTransfer and is defined in the process control messaging system architecture 300 level. The interface ILargeDataTransfer allows instantiation of the large data transfer operation.

In the present example, the defined methods include, but are not limited to, BeginTransfer, EndTransfer, Pause, Resume and Cancel. The BeginTransfer is an asynchronous method called by the requesting client (ResponseEndpoint) to start a large data transfer operation. The BeginTransfer method utilizes an operation transfer specifier that contains the details of the large data transfer operation, an asynchronous callback to be called when the large data transfer operation is complete, and a user-provided object that distinguishes each particular asynchronous large data transfer operation request from other large data transfer requests. The BeginTransfer method returns an IAsyncResult that represents the large data transfer asynchronous operation, which, at the time, could still be pending.

The EndTransfer method is a method the requesting client calls upon completion of the large data transfer to read the completion result. The EndTransfer method otherwise waits for the pending asynchronous large data transfer operation to complete, and utilizes the reference to the pending asynchronous large data transfer request to finish which is returned by the BeginTransfer method when the asynchronous operation is started, IAsyncResult. The EndTransfer method further return the large data transfer operation result. The Pause method is a method the requesting client calls to pause a specified asynchronous large data transfer operation. The Pause method utilizes the reference to the pending asynchronous request to pause as returned by the BeginTransfer method when the asynchronous large data transfer operation is started, IAsyncResult. The Resume method is a method the requesting client endpoint calls to resume a paused specified asynchronous large data transfer operation. The Resume method likewise utilizes the reference to the pending asynchronous large data transfer request to resume as returned by the BeginTransfer method when the asynchronous large data transfer operation is started, IAsyncResult. The Cancel method is a method the requesting client calls to cancel a specified asynchronous large data transfer operation, and utilizes the reference to the pending asynchronous large data transfer request to cancel which was returned by the BeginTransfer method when the asynchronous large data transfer operation is started, IAsyncResult.

The following is an example for the process control messaging system architecture 300 creating, instantiating and initiating a large data transfer:

Create the Large data transfer specifier using the LargeDataTransferSpecifierBuilder:

-   -   var specifier=LargeDataTransferSpecifierBuilder.Build(filePath,         destinationPlatform);

Instantiate the TransferRequestSender:

-   -   var ldtSender=new TransferRequestSender(localEndPoint, new         ServerFactory( ));

Initiate the Transfer:

-   -   var operation=ldtSender.BeginTransfer(specifier, ar=>{ }, null,         true);     -   operation.StateChanged+=(s, e)=>Console.WriteLine(e.State);     -   var result=ldtSender.EndTransfer(operation);     -   Console.WriteLine((“LDT operation result: {0}”,         result.Status.IsSuccessful);

FIG. 6 depicts an example of common interfaces implemented by the process control messaging system architecture 300. As seen in FIG. 6, the common interfaces include, but are not limited to, Topic, TopicData, Status, UserContext, IAsyncOperation, AsyncOperationStateChangedEventArgs and AsyncOperationState. The Topic interface is a class that represents the topic identifier and s used as Topic<string>. The TopicData interface is a class that represents the topic data. The Status interface is a status object used in responses, such as to guarantee (or not guarantee) delivery of a message. The UserContext interface is a class that contains user contact information. The UserContext interface further implements defined methods, IsEqual(UserContext), that compares one UserContext to another, and returns true if the contexts are the same. The IAsyncOperation interface represents an asynchronous operation and provides an event for the asynchronous operation state changing notification, StateChanged<AsyncOperationStateChangedEventArgs>, which occurs when an asynchronous operation state is changed. The AsyncOperationStateChangedEventArgs, in turn, is a class of asynchronous operation state changed arguments. The AsynchOperationState provides asynchronous operation state information with the properties of an asynchronous operation identification (OperationID), the type of asynchronous operation (Type), and the progress value of the asynchronous operation (Progress).

As noted with respect to FIG. 1, in some embodiments the server 150 may act as an enrollment server for registering and enrolling industrial computing devices 112, 113 in the process control messaging service. An administrator of the process control messaging service may register each industrial computing device. For example, newly-licensed industrial computing devices 112, 113 may be added to the process control messaging network, and registered at that time using a unique identifier associated with the industrial computing device. At this time, registration may define any restrictions or authorizations on the industrial computing device, including, but not limited to, subscriptions to other devices it may communicate with on the process control messaging network, restrictions to specific process control messaging services, etc. Further, in the case of a guest industrial computing device (e.g., as may be used by an external contractor working in the process control system) an industrial computing device may be restricted to temporary access to the process control messaging service, as opposed to permanent access. The registration process may also inform the industrial computing device of the network address of the enrollment server, such that the enrollment server is well-known to the industrial computing device.

In one embodiment, the enrollment service is provided using a communication module in the wireless interface of each device on the process control messaging network in communication with a single, well-known endpoint, such as the server 150. Each time an industrial computing device connects to the process control messaging network (e.g., via a wireless access point or via USB), the enrollment service verifies registration, performs notifications to other endpoints enrolled on the process control messaging based on subscription status (if any), and periodically pings the industrial computing device to maintain connection and enrollment status.

FIG. 7 depicts an example of the enrollment process 400 between an industrial computing device and the enrollment server 150. In one embodiment, the enrollment process 400 is the first activity after a platform, such an industrial computing device, starts/connects to the process control messaging system architecture 300. The platform is otherwise unable to perform any services offered by the process control messaging system architecture 300 without a successful enrollment. As mentioned, the enrollment server is a well-known endpoint to the different platforms. As such, in a multi-platform environment, there is a designated enrollment server that is capable of validating enrollment requests for all platforms when they connect and start up. The enrollment server is capable of querying services. such as licensing services, in order to validate connecting platforms.

Once there is a need for a registered industrial computing device to participate in the process control messaging network (i.e., as a client/endpoint), the registered industrial computing device, upon connection of the platform to the process control messaging network, begins the enrollment process as a local operation 402 by automatically initiating a request to the enrollment server for enrollment of the platform. The local operation attempts to reach the enrollment server 404. If the enrollment server is not available or not reachable, no enrollment is performed and no process control messaging services are possible at that time. Enrollment from a platform directly connected to a personal computer platform in a peer-to-peer relationship (e.g., USB cable connection) causes the personal computer platform to attempt to route (forward) the enrollment request to the enrollment server 150, provided the personal computer platform is not itself the enrollment server 150.

The enrollment server verifies the registration of the industrial computing device with the process control messaging service, and publishes the addresses of other devices on the process control messaging network based on the subscription status of the enrolled industrial computing device 406. The enrollment of the industrial computing device is recorded, with the enrollment server periodically pinging the industrial computing device to maintain enrollment connection and status 408. At this time, the enrollment server may notify the process control messaging services of the enrollment of the industrial computing device. For example, the enrollment service may notify an upgrade service that a specific industrial computing device has connected/enrolled, and the upgrade service can, in turn, inform the industrial computing device of any pending upgrades for its platform.

Having enrolled a registered industrial computing device 112 in the process control messaging service, the endpoints (i.e., destinations) become known to the enrolled (participating) device, as least insofar as allowed by the subscription status of the enrolled device, no matter if the endpoints are on the same physical devices (e.g., industrial computing device-to-industrial computing device), or different physical devices (e.g., industrial computing device-to-field device), or different platforms. Knowing the endpoints allows a participating industrial computing device to structure messages according to the destination platform. For example, if the participating industrial computing device is to communicate with a Fieldbus field device, the industrial computing device uses the process control communication protocol layer of the process control messaging system architecture 300 to generate the message in the Fieldbus protocol. Similar, if the participating industrial computing device is to communicate with a HART field device, the industrial computing device uses the process control communication protocol layer of the process control messaging system architecture 300 to generate the message in the HART protocol.

Once the message has been generated, the industrial computing device 112 uses the process control messaging protocol layer of the process control messaging system architecture 300 to wrap the generated message in the protocol of process control messaging service. In one embodiment, the message may be wrapped such that the message forms the payload of a packet in the protocol of the process control messaging service, with the process control messaging service protocol having a header with information on the process control communication protocol (e.g., Fieldbus, HART) and a network address or identification of the destination device.

Once the wrapped message is transmitted to the process control messaging network using the process control messaging protocol, the process control messaging network may unwrap, or decode, the message into the communication protocol of the destination device using the information in the header, and route/forward the unwrapped message to the destination device. Once the message is delivered to the destination device (platform), the message may be further routed to a particular process based on the message topic and/or application (discussed below). For example, based on a specified topic-application, the message is sent to the application for further processing. The application may optionally copy the message (or file, in the case of large data transfers), and then move the message to a particular process based on the topic designated in the message.

In an exemplary general scenario of an enrolled industrial computing device participating in the process control messaging service, a portable industrial computing device has need to participate in the process control messaging network in order to perform work activities. The industrial computing device is registered with and enrolled in the process control messaging network using the registration and enrollment services described above. Upon enrollment, a software application on the industrial computing device makes a request to a messaging service of the process control messaging services to establish communications with another industrial computing device. An inquiry is sent from the requesting industrial computing device to the well-known process control messaging service, and a listing of connected devices is queries and provided by the enrollment service. Using the process control messaging system architecture 300, the requesting industrial computing device generates and wraps its message for the destination device as described above. In turn, the destination device may use its process control messaging system architecture 300 to generate and wrap a response message.

FIG. 8 is a sequence diagram 500 depicting an example request/response operation. The particular request/response operation is for time synchronization of an industrial computing device having a client application as a requesting endpoint and a time synchronization server as the receiving endpoint, though it should be understood that the example scenario may be readily modified for other request/response operations using other client applications and services, including, but not limited to request/responses involving multiple endpoints (e.g., messaging multiple industrial computing devices 112, 113). Referring to FIG. 8, the TimeSyncServer performs initialization and bootstrapping of the RequestReceiverBase class 502. Thereafter, the endpoint client sends an asynchronous GetDateTime request 504, and the TimeSyncClient application supplies necessary specifiers 506. The TimeSyncClient calls the BeginRequest method of the RequestSenderBase 508, and the RequestSenderBase posts the request to the client instance of a MessageBroker 510. The client instance of the MessageBroker sends the message using the messaging infrastructure of the process control messaging system 512. On the server side, a server instance of MessageBroker receives the message from the messaging infrastructure 514, and the server instance of the MessageBroker returns the message to the RequestReceiverBase on a peek method call 516. The RequestReceiverBase receives the message 518, and calls its own abstract method ProcessRequest 520, which, as described above, is an abstract method to be implemented by the endpoint, TimeSyncServer, inheriting from the RequestReceiverBase. The server generates DateTime response 522, and the TimeSyncServer sends the response to RequestReceiverBase by the calling SendResponse method 524. The RequestReceiverBase posts the response to the server instance of the MessageBroker 526. The RequestSenderBase receives the response message and calls a Callback method 528. The TimeSyncClient receives the response via callback from BeginRequest 530, where the Callback method is implemented by the TimeSyncClient. The TimeSyncClient calls the EndRequest method of the RequestSenderBase 532, and the client receives a GetDateTime response 534. As another embodiment, once communications have been established, the software application of the requesting industrial computing device issues a request to the process control messaging services to transfer multiple large data files from the requesting industrial computing device to the destination industrial computing device. A listing of data files is requested by either the requesting or destination industrial computing device. A file transfer service is then activated based on the request.

FIG. 9 is a sequence diagram 600 depicting an example large data transfer (LDT) operation. The particular large data transfer operation, though it should be understood that the example scenario may be readily modified for other large data transfer operations using other client applications and services, including, but not limited to large data transfers to multiple destinations (e.g., updates from the external cloud 210 to the industrial computing devices 112, 113). Referring to FIG. 9, an LDT client performs a large data transfer from LDT Source to LDT Destination. An LDT Request Receiver performs startup and initialization routines 602, and a LDT Data Server performs startup and initialization routines 604. The LDT Client starts a transfer operation 606, and the BeginTransfer method of the LDT Request Sender providing an LDTSpecifier with the LDT Source/Destination 608. The LDT Request Sender calls the BeginRequest method of the RequestSenderBase providing the RequestSpecifier 610. The RequestSenderBase sends the Request Message to the RequestReceiverBase using the messaging infrastructure 612, and the RequestReceiverBase receives the RequestMessage, processes it, and calls the ProcessRequest abstract method 614. The LDT Request Receiver ProcessRequest method implementation calls the InstantiateTransferring message of the LDT Service 616, and the LDT Service creates a transfer session and sends the data request message to the LDT Data Server using the messaging infrastructure 618.

The LDT Data Server receives the Data Request Message, handles it, and sends Data to the LDT Service via the messaging infrastructure 620. In turn, the LDT Service receives the Data, handles it, and sends a data request message for the next portion of the Data 622. The LDT Service generates a StateChanged event 624, and the LDT Request Receiver calls the NotifyStateChanged method of the RequestReceiverBase 626. The RequestReceiverBase NotifyStateChanged method implementation sends the progress message to the RequestSenderBase using the messaging infrastructure 628. The RequestSenderBase receives the Progress message and generates a ProgressChangedEvent 630.

The LDT Service, upon handling the last portion of the Data, closes the LDT session and generates the StateChanged(Complete) event 632, and the LDT Request Receiver calls the SendResponse method of the RequestReceiverBase 634. The RequestReceiverBase SendResponse method implementation sends a RequestComplete message to the RequestSenderBase using the messaging infrastructure 636. The RequestSenderBase receives the RequestComplete message and calls the LDT Client's callback method 638, and, in turn, the LDT Client calls the EndTransfer method of the LDT Request Sender 640. The LDT Request Sender calls the EndRequest method of the RequestSenderBase 642, and the RequestSenderBase returns the RequestResult on the EndRequest method 644. The LDT Request Sender returns the Transfer Result on the EndTransfer method 646.

Further embodiments, which should be understood from the above example, may likewise be implemented after enrollment using the process control messaging system. For example, the software application of the requesting industrial computing device issues a request to the process control messaging service to begin real-time/instant messaging with a destination industrial computing device. The registration service of the process control messaging service provides a listing of connected/enrolled devices to the requesting industrial computing device. The requesting industrial computing device is then capable of peer-to-peer messaging with the enrolled destination industrial computing device.

Once the software application of the requesting industrial computing device is done with the process control messaging services, the software application issues a request to end communications with the other device. In some cases, connected device has lost connection with the network. In either case, the registration service updates its internal connected/enrolled devices list. A notification is provided indicating the device is no longer connected to the process control messaging network.

FIG. 6 illustrates a block diagram of an example industrial computing device 112, 113. The industrial computing device 112, 113 may be a handheld device or a portable computing device such as a laptop computer, a tablet computer, a mobile device smart-phone, a personal digital assistant (PDA), a wearable computing device, etc. The industrial computing device 112, 113 may include a display 84, one or more processors or CPUs 88, a memory 52, a random-access memory (RAM) 90, an input/output (I/O) circuit 92, and a communication unit 86 to transmit and receive data via a local area network, wide area network, or any other suitable network. The communication unit 86 may include an NFC or RFID reader 98 to receive and decode NFC or RFID signals. The industrial computing device 112, 113 may communicate with the controllers 11, the server 150, and/or any other suitable computing device.

The memory 52 may include an operating system 78, a control unit 94 for controlling the display 88 and communicating with process control devices, and an authentication/authorization module 96 for authenticating a user and determining a level of authorization for the user. In some embodiments, the authentication/authorization module 96 may determine whether a user has access to a connected process control device as well as the types of operations the user is authorized to perform on the connected process control device. Once it is determined that the user is authorized to execute a particular function to perform an operation on the connected process control device (e.g., a configuration function), the control unit 94 may control configuration of the connected process control device by receiving inputs from the user, displaying outputs from the connected process control device, and communicating with the connected process control device to adjust settings on the connected process control device.

To authorize users and industrial computing devices to access process control devices, the server 150 generates permissions which specify a level of access to a particular process control device. For example, a first permission may allow access to Field Device A for reading data from the device and for executing monitoring functions. A second permission may allow access to Field Device B for reading and writing data to the device and for executing calibration and configuration functions. Additionally, the second permission may specify a time duration (e.g., 1 hour) and a plant area in which the user may access the process control device. In some embodiments, a system administrator may interact with the server 150 to generate the permissions.

In addition to generating the permissions, the server 150 may assign each permission to one or several users and to one or several industrial computing devices. For example, the system administrator may grant the first permission to a first subset of users and a first subset of industrial computing devices in the process plant. In some scenarios, each user who is granted the same permission may have a same or similar job function with the process plant. For example, each of the maintenance technicians in a process plant may be assigned the same permissions. In some embodiments, the indications of permissions, users in the process plant, industrial computing devices within the process plant, and associations between the permissions, users, and industrial computing devices may be stored in one or several databases communicatively coupled to the server 150.

The following additional considerations apply to the foregoing discussion. Throughout this specification, actions described as performed by any device or routine generally refer to actions or processes of a processor manipulating or transforming data according to machine-readable instructions. The machine-readable instructions may be stored on and retrieved from a memory device communicatively coupled to the processor. That is, methods described herein may be embodied by a set of machine-executable instructions stored on a computer readable medium (i.e., on a memory device). The instructions, when executed by one or more processors of a corresponding device (e.g., a server, a user interface device, etc.), cause the processors to execute the method. Where instructions, routines, modules, processes, services, programs, and/or applications are referred to herein as stored or saved on a computer readable memory or on a computer readable medium, the words “stored” and “saved” are intended to exclude transitory signals.

Further, while the terms “operator,” “personnel,” “person,” “user,” “technician,” and like other terms are used to describe persons in the process plant environment that may use or interact with the systems, apparatus, and methods described herein, these terms are not intended to be limiting. Where a particular term is used in the description, the term is used, in part, because of the traditional activities in which plant personnel engage, but is not intended to limit the personnel that could be engaging in that particular activity.

Additionally, throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.

Unless specifically stated otherwise, discussions herein using words such as “processing,” “computing,” “calculating,” “determining,” “identifying,” “presenting,” “causing to be presented,” “causing to be displayed,” “displaying,” or the like may refer to actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, biological, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.

When implemented in software, any of the applications, services, and engines described herein may be stored in any tangible, non-transitory computer readable memory such as on a magnetic disk, a laser disk, solid state memory device, molecular memory storage device, or other storage medium, in a RAM or ROM of a computer or processor, etc. Although the example systems disclosed herein are disclosed as including, among other components, software and/or firmware executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components could be embodied exclusively in hardware, exclusively in software, or in any combination of hardware and software. Accordingly, persons of ordinary skill in the art will readily appreciate that the examples provided are not the only way to implement such systems.

Thus, while the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, it will be apparent to those of ordinary skill in the art that changes, additions or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the invention.

It should also be understood that, unless a term is expressly defined in this patent using the sentence “As used herein, the term ‘_(———)’ is hereby defined to mean . . . ” or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be interpreted to be limited in scope based on any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this patent is referred to in this patent in a manner consistent with a single meaning, that is done for sake of clarity only so as to not confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by reciting the word “means” and a function without the recital of any structure, it is not intended that the scope of any claim element be interpreted based on the application of 35 U.S.C. §112(f) and/or pre-AIA 35 U.S.C. §112, sixth paragraph.

Moreover, although the foregoing text sets forth a detailed description of numerous different embodiments, it should be understood that the scope of the patent is defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possible embodiment because describing every possible embodiment would be impractical, if not impossible. Numerous alternative embodiments could be implemented, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims. 

1. A platform-to-platform method of communication between industrial computing devices in a process control system comprising: enrolling a requesting industrial computing device platform in a process control messaging service in response to a request for enrollment from the requesting industrial computing device platform, the requesting industrial computing device platform and the process control messaging service each having a framework of a communication protocol of a destination industrial computing device platform layered above a communication protocol of the process control messaging service, and the protocol of the process control messaging service layered above a network communications protocol; receiving a wrapped message from the requesting industrial computing device platform via a communication transport type associated with the networking communications protocol, wherein the message is generated by the requesting industrial computing device platform in the communication protocol of the destination industrial computing device platform and wrapped in the communication protocol of the process control messaging service having a header comprising the identification of a destination industrial computing device platform and the communication protocol of the destination industrial computing device platform; decoding the wrapped message into the communication protocol of the destination industrial computing device platform; and forwarding the decoded wrapped message to the destination industrial computing device platform.
 2. The method of claim 1, wherein enrolling the industrial computing device platform comprises: receiving the request for enrollment from the requesting industrial computing device platform at an enrollment server on a process control messaging network, the request comprising identification of the requesting industrial computing device platform and identification of the enrollment server, the process control messaging network being logically independent of a digital process control network for controlling field devices within the process control system; verifying registration of the requesting industrial computing device platform with the process control messaging service; granting participation of the requesting industrial computing device platform with the process control messaging service if the requesting industrial computing device platform was previously registered with the process control messaging service; and notifying other industrial computing device platforms enrolled in the process control messaging service that the requesting industrial computing device platform is enrolled based on a subscription status of the requesting industrial computing device, the subscription status identifying those industrial computing device platforms permitted to communicate with the requesting industrial computing device.
 3. The method of claim 2, further comprising registering the requesting industrial computing device platform with the process control messaging service prior to enrolling the requesting industrial computing device, wherein registering comprises: assigning a unique identifier with the requesting industrial computing device, the unique identifier uniquely identifying the requesting industrial computing device among other industrial computing devices registered with the process control messaging service; defining restrictions and/or authorizations to the requesting industrial computing device; and notifying the requesting industrial computing device of a network address of the enrollment server.
 4. The method of claim 2, wherein registration of the requesting industrial computing device platform comprises temporary access to the process control messaging service.
 5. The method of claim 2, wherein registration of the requesting industrial computing device platform comprises permanent access to the process control messaging service.
 6. The method of claim 2, wherein registration of the requesting industrial computing device platform comprises access to particular ones of services offered by the process control messaging service.
 7. The method of claim 6, wherein services offered by the process control messaging service comprise: a messaging service to allow a plurality of industrial computing device platforms to communicate with each other, and a data file transfer service to allow a plurality of industrial computing device platforms to transfer data files with each other.
 8. The method of claim 2, wherein enrolling the industrial computing device platform comprises automatically enrolling the industrial computing device platform upon connection of the industrial computing device platform to the process control messaging network.
 9. The method of claim 8, wherein the connection of the industrial computing device platform to the process control messaging network is a wireless connection via a wireless communication channel to a network access point of the process control messaging network.
 10. The method of claim 8, wherein the connection of the industrial computing device platform to the process control messaging network is a wired connection via a wired communication channel to a network access point of the process control messaging network.
 11. The method of claim 2, wherein enrolling the industrial computing device platform comprises enrolling the industrial computing device platform upon receipt of a routing of the request for enrollment from a personal computing platform hardwired to the requesting industrial computing device platform, wherein the personal computing platform forwards the request for enrollment from the requesting industrial computing device platform upon hardwire connection of the requesting industrial computing device platform to the personal computing platform.
 12. The method of claim 11, wherein the requesting industrial computing device platform is hardwired via Universal Serial Bus (USB) to the personal computing platform.
 13. The method of claim 2, further comprising: receiving from the requesting industrial computing device platform, a request to transfer one or more data files from the requesting industrial computing device platform to the destination industrial computing device platform; and activating a transfer of the one or more data files from the requesting industrial computing device platform to the destination industrial computing device platform.
 14. The method of claim 2, further comprising: receiving from the destination industrial computing device platform, a request to transfer one or more data files from the destination industrial computing device platform to the requesting industrial computing device platform; and activating a transfer of the one or more data files from the destination industrial computing device platform to the requesting industrial computing device platform.
 15. The method of claim 2, further comprising: receiving from the requesting industrial computing device platform, a request for real-time, peer-to-peer messaging with another industrial computing device platform; providing to the requesting industrial computing device platform a list of other industrial computing device platforms enrolled in the process control messaging service; and activating a transmission of a real-time message from the requesting industrial computing device platform to one or more other industrial computing device platforms.
 16. The method of claim 1, wherein the destination industrial computing device platform comprises one or more industrial computing device platforms, and wherein decoding the wrapped message into the communication protocol of the destination industrial computing device platform comprises decoding the wrapped message into the communication protocol of each of the one or more destination industrial computing devices platforms, and wherein forwarding the decoded wrapped message comprises forwarding the decoded wrapped message to each of the one or more industrial computing device platforms.
 17. A system for platform-to-platform communication between industrial computing devices, comprising: an enrollment server adapted to enroll a requesting industrial computing device platform in a process control messaging service in response to a request for enrollment from the requesting industrial computing device platform, the requesting industrial computing device platform and the process control messaging service each having a framework of a communication protocol of a destination industrial computing device platform layered above a communication protocol of the process control messaging service, and the protocol of the process control messaging service layered above a network communications protocol; and a process control messaging system architecture adapted to: receive a wrapped message from the requesting industrial computing device platform via a communication transport type associated with the networking communications protocol, wherein the message is generated by the requesting industrial computing device platform in the communication protocol of the destination industrial computing device platform and wrapped in the communication protocol of the process control messaging service having a header comprising the identification of a destination industrial computing device platform and the communication protocol of the destination industrial computing device platform; decode the wrapped message into the communication protocol of the destination industrial computing device platform; and forward the decoded wrapped message to the destination industrial computing device platform.
 18. The system of claim 17, wherein the process control messaging system architecture is further adapted to: receive the request for enrollment from the requesting industrial computing device platform at an enrollment server on a process control messaging network, the request comprising identification of the requesting industrial computing device platform and identification of the enrollment server, the process control messaging network being logically independent of a digital process control network for controlling field devices within the process control system; verify registration of the requesting industrial computing device platform with the process control messaging service; grant participation of the requesting industrial computing device platform with the process control messaging service if the requesting industrial computing device platform was previously registered with the process control messaging service; and notify other industrial computing device platforms enrolled in the process control messaging service that the requesting industrial computing device platform is enrolled based on a subscription status of the requesting industrial computing device, the subscription status identifying those industrial computing device platforms permitted to communicate with the requesting industrial computing device.
 19. The system of claim 18, wherein the enrollment server is further adapted to register the requesting industrial computing device platform with the process control messaging service prior to enrolling the requesting industrial computing device, wherein registration by the enrollment server comprises: assigning a unique identifier with the requesting industrial computing device, the unique identifier uniquely identifying the requesting industrial computing device among other industrial computing devices registered with the process control messaging service; defining restrictions and/or authorizations to the requesting industrial computing device; and notifying the requesting industrial computing device of a network address of the enrollment server.
 20. The system of claim 18, wherein registration of the requesting industrial computing device platform comprises temporary access to the process control messaging service.
 21. The system of claim 18, wherein registration of the requesting industrial computing device platform comprises permanent access to the process control messaging service.
 22. The system of claim 18, wherein registration of the requesting industrial computing device platform comprises access to particular ones of services offered by the process control messaging service.
 23. The system of claim 22, wherein services offered by the process control messaging service comprise: a messaging service to allow a plurality of industrial computing device platforms to communicate with each other, and a data file transfer service to allow a plurality of industrial computing device platforms to transfer data files with each other.
 24. The system of claim 18, wherein the enrollment server is further adapted to automatically enroll the industrial computing device platform upon connection of the industrial computing device platform to the process control messaging network.
 25. The system of claim 8, wherein the connection of the industrial computing device platform to the process control messaging network is a wireless connection via a wireless communication channel to a network access point of the process control messaging network.
 26. The system of claim 8, wherein the connection of the industrial computing device platform to the process control messaging network is a wired connection via a wired communication channel to a network access point of the process control messaging network.
 27. The system of claim 18, wherein the enrollment server is further adapted to enroll the industrial computing device platform upon receipt of a routing of the request for enrollment from a personal computing platform hardwired to the requesting industrial computing device platform, wherein the personal computing platform forwards the request for enrollment from the requesting industrial computing device platform upon hardwire connection of the requesting industrial computing device platform to the personal computing platform.
 28. The system of claim 27, wherein the requesting industrial computing device platform is hardwired via Universal Serial Bus (USB) to the personal computing platform.
 29. The system of claim 18, wherein the process control messaging system architecture is further adapted to: receive from the requesting industrial computing device platform, a request to transfer one or more data files from the requesting industrial computing device platform to the destination industrial computing device platform; and activate a transfer of the one or more data files from the requesting industrial computing device platform to the destination industrial computing device platform.
 30. The system of claim 18, wherein the process control messaging system architecture is further adapted to: receive from the destination industrial computing device platform, a request to transfer one or more data files from the destination industrial computing device platform to the requesting industrial computing device platform; and activate a transfer of the one or more data files from the destination industrial computing device platform to the requesting industrial computing device platform.
 31. The system of claim 18, wherein the process control messaging system architecture is further adapted to: receive from the requesting industrial computing device platform, a request for real-time, peer-to-peer messaging with another industrial computing device platform; provide to the requesting industrial computing device platform a list of other industrial computing device platforms enrolled in the process control messaging service; and activate a transmission of a real-time message from the requesting industrial computing device platform to one or more other industrial computing device platforms.
 32. The system of claim 17, wherein the destination industrial computing device platform comprises one or more industrial computing device platforms, and wherein the process control messaging system architecture is further adapted to: decode the wrapped message into the communication protocol of each of the one or more destination industrial computing devices platforms; and forward the decoded wrapped message to each of the one or more industrial computing device platforms.
 33. The system of claim 17 further comprising one or more industrial computing device platforms each communicatively coupled to the enrollment server and the process control messaging architecture, each industrial computing device platform adapted to: receive the decoded wrapped message, the decoded wrapped message identifying a topic and an application; directing the decoded wrapped message to the application identified in the decoded wrapped message for processing; and directing the decoded wrapped message from the application to a process based on the topic identified in the decoded wrapped message.
 34. The system of claim 17, wherein the requesting industrial computing device platform resides on a first network and the destination industrial computing device platform resides on a second network isolated from the first network, the system further comprising an intermediary industrial computing device platform communicatively coupled to the process control messaging architecture and the requesting industrial computing device platform, the intermediary industrial computing device platform adapted to: maintain isolation between the first and second networks; receive the decoded wrapped message, the decoded wrapped message identifying the destination industrial computing device platform on the second network; and port redirecting the message to the destination industrial computing device platform identified in the decoded message. 